docs/docs/users/reference/env_variables.md (1)

67-67: Consider adding a Lotus-interop note for operators.

Optional: mention the Lotus equivalent (LOTUS_FEES_FIP0115HEIGHT) to reduce migration confusion in mixed deployments.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/docs/users/reference/env_variables.md` at line 67, Add a brief
Lotus-interop note alongside the FOREST_FEES_FIP0115HEIGHT entry clarifying the
equivalent Lotus environment variable LOTUS_FEES_FIP0115HEIGHT so operators
migrating or running mixed deployments understand the mapping; update the table
cell or a short footnote to mention "Lotus equivalent: LOTUS_FEES_FIP0115HEIGHT"
and indicate it has the same semantics (integer epoch, -1 to disable,
consensus-breaking/testing only).

src/chain/store/base_fee.rs (1)

20-21: Add explicit runtime warning when the consensus override is enabled.

FOREST_FEES_FIP0115HEIGHT is consensus-breaking, but activation is currently silent. A one-time warning here would reduce operator misconfiguration risk.

🔧 Suggested change

 use std::sync::LazyLock;
+use tracing::warn;

 static FIP0115_HEIGHT: LazyLock<ChainEpoch> =
-    LazyLock::new(|| env_or_default("FOREST_FEES_FIP0115HEIGHT", -1));
+    LazyLock::new(|| {
+        let height = env_or_default("FOREST_FEES_FIP0115HEIGHT", -1);
+        if height >= 0 {
+            warn!(
+                "FOREST_FEES_FIP0115HEIGHT={} enabled; this is consensus-breaking and intended for testing only",
+                height
+            );
+        }
+        height
+    });

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/chain/store/base_fee.rs` around lines 20 - 21, FIP0115_HEIGHT is being
set silently from env_or_default("FOREST_FEES_FIP0115HEIGHT", -1); change the
LazyLock initialization so that when the resolved value is not the default (-1)
it emits a one-time runtime warning (e.g., via log::warn! or the project logger)
informing operators that a consensus override is enabled and which epoch value
is set; keep the value semantics the same but ensure the warning happens inside
the LazyLock::new closure for FIP0115_HEIGHT so it runs once at startup when the
env var is active.